Exceptions during processing

Processing exceptions occur when the system cannot process a document or excludes elements of the file during processing. When a processing exception occurs, the system records a processing exception that includes information about the processing job, the affected file, and the cause of the exception. To view processing exceptions, run a Processing Exception Report. You can also search for exceptions in INSPECT and REVIEW.

Some files produce non-recoverable exceptions, such as unsupported files. As needed, you can slipsheet these files during production. With non-specific errors, you can attempt to reprocess the document during INSPECT. In other cases, you could change a document's state outside of Epiq Discovery (for example, by decrypting a file). Then, collect and process the updated file.

The following list of exceptions describes the exception and provides possible remediation where applicable.

Exception	Description
Corrupted File	File contains structural problems. Obtain a new copy of the file and attempt to recollect and reprocess.
Empty File	File contains no data.
Encrypted File	File is protected and cannot be read. Outside of Epiq Discovery, you can attempt to decrypt the file or remove the password. You can then collect and process the new copy of the file.
Exceeded max processing attempts	File was attempted to be processed, but failed to process after 3 attempts.
Extracted Text Excluded Due to Size	File exceeds the maximum amount of allowable extracted text. Verify the file size in the original file to make sure it does not exceed this maximum. If the file size is less than the maximum, in INSPECT, you can Reprocess the file.
Failed to Extract Content	The system identified the document as an encrypted or unparsed document where metadata cannot be extracted. Check the original document to verify that it can be opened. If so, in INSPECT, you can Reprocess the file. Or, obtain a new copy of the file to collect and process.
File Contains Excluded Items	The system intentionally excluded small embedded images that are immaterial to content in order to improve processing performance.
File Contains Modern Attachment	The Outlook email file contains one of the following modern attachments: a OneDrive file link that was shared. a file link that was copied from OneDrive.
File Not Copied	The Native file failed to save to Epiq Discovery properly while it was being collected or extracted from the Source location.
Microsoft Teams Data Detected	The system identified the file as Microsoft Teams data.
Not Extracted Due to Set Threshold	Embedded Images were not extracted from the document per the current Project Settings.
OCR Text Truncated Due to Size	Text obtained during OCR exceeds the maximum amount of allowable text.
Processing Exception	The system returned a general error on the file. In INSPECT, you can Reprocess the file. Or, obtain a new copy of the file to collect and process.
System Link File	File appears to be a system link or shortcut file. System link files remain unprocessed for security reasons.
Text Unavailable	File appears to have no viable text to extract and may not contain text. If text is present, then you can image and OCR the file.
Track Changes Truncated to 75MB; Extracted Text Truncated Due to Size	Track changes exceeded 75 MB in a Word, Excel, or Open Office file (ODT, OTT, ODS, ODT, or OTT).
Unable to Create Image for this Document	File appears corrupt or unsupported. In INSPECT, you can Reprocess the file. Or, obtain a new copy of the file to collect and process.
Unable to Parse File	Unable to read the file. In INSPECT, try to Reprocess the file. Or, obtain a new copy of the file to collect and process.
Unsupported File	The system cannot process the file type.
Virus Infected File	The system identified the file as containing a virus or other malware. Outside of Epiq Discovery, try to disinfect the original file. Or, obtain a new copy of the file to collect and process.